Skip to content

Conversation

@teallarson
Copy link
Contributor

@teallarson teallarson commented Feb 2, 2026

Contains docs updates that align with the changes in the toolkit picker here and here.

This should ideally not be merged until approximately when those changes go live.


Note

Low Risk
Primarily copy/link updates with minimal code impact; main risk is broken navigation if any updated anchors/URLs are incorrect.

Overview
Renames the “Starter” tool type to “Unoptimized” across the docs site, including the Types of Tools guide, glossary, changelog entry, and the starter-tool warning callout.

Updates toolkit picker/filter UI strings (type-config.tsx, use-toolkit-filters.ts) to display “Arcade Unoptimized” / “Arcade Unoptimized MCP Server” and repoints related doc links to the new #unoptimized-tools anchor; also refreshes public/llms.txt to reflect the new terminology.

Written by Cursor Bugbot for commit 45ba4c0. This will update automatically on new commits. Configure here.

@vercel
Copy link

vercel bot commented Feb 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Feb 5, 2026 2:40pm

Request Review

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style Review

Found 4 style suggestion(s).

Powered by Vale + Claude

teallarson and others added 4 commits February 2, 2026 09:42
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
- Optimized tools

The distinction is merely a matter of how they are designed. Both types of tools can be used seamlessly in the same way. There is no difference in their interfaces, the way they are called, or how you interact with them through the Arcade [Dashboard](https://api.arcade.dev/dashboard/) or the Arcade [SDK clients](/references).
The distinction is merely a matter of how Arcade designs them. Both types of tools can be used seamlessly in the same way. No difference exists in their interfaces, the way they are called, or how you interact with them through the Arcade [Dashboard](https://api.arcade.dev/dashboard/) or the Arcade [SDK clients](/references).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how Arcade designs them

This was a vale suggestion, but I think we have some community contributions so this isn't quite true always? Except maybe it is because the Optimized ones are optimized by us?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good discussion to have now. The community toolkits was an idea where we would show non-arcade toolkits in our docs, kind of like a marketplace. We are not doing that, and with MCP servers, I think we will not do it in the short term, so I'm not sure if it's valid to keep that category.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, cool, then I don't think this suggestion is an issue :)

Since they require careful design and evaluation, Optimized tools take time and effort to build. Arcade understands that your Agent or chatbot project might need capabilities not yet covered by Arcade's Optimized MCP Servers. For this reason, Arcade also offers low-level Unoptimized MCP Servers (formerly known as Starter MCP Servers).

## Starter tools
<span id="starter-tools" />
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was a weird suggestion from Cursor to not break existing links. It's clever I guess, but I'm not sure it's right.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ummm, I don't get why there is an empty span here.

**Toolkits**

- `[feature - 🚀]` Introduce [Starter Tools](/guides/create-tools/improve/types-of-tools), a new type of tool that mirrors the original HTTP API design of the upstream service.
- `[feature - 🚀]` Introduce [Unoptimized tools](/guides/create-tools/improve/types-of-tools), a new type of tool that mirrors the original HTTP API design of the upstream service.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we want to back-edit the changelog...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Umm, I think it's ok.


#### Starter tools
<span id="starter-tools" />

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

again with clever link stuff

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link is generated automatically by Nextra for markdown titles. I don't understand this span.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cursoragent please remove the empty spans added here and elsewhere in this PR's diff

Copy link

@cursor cursor bot Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update: empty spans removed

  • Removed the empty <span id="starter-tools" /> elements from:
    • app/en/guides/create-tools/improve/types-of-tools/page.mdx
    • app/en/resources/glossary/page.mdx
  • Committed and pushed the fix to plt-1035-unoptimized-terminology (docs: remove empty span anchors).
  • Verified by running pnpm test (all link/docs tests passed).

Open in Cursor Open in Web

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(I think it was so the browser can still anchor to the old link? But I also think it was cursor being too clever.)

@teallarson teallarson changed the title docs: rename Starter tools to unoptimized docs: rename Starter tools to Unoptimized Feb 2, 2026
@teallarson
Copy link
Contributor Author

@nearestnabors this PR is blocked on the monorepo updates, but the content is worthy of a review in the meantime

@teallarson teallarson marked this pull request as ready for review February 4, 2026 22:53
Copy link
Contributor

@sdserranog sdserranog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some nits, but this is good to go. :shipit:

Co-authored-by: Teal Larson <LARSON.TEAL@GMAIL.COM>
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

before using it in production.{" "}
<a href="/guides/create-tools/improve/types-of-tools">Read more</a> about
Optimized vs Starter tools.
Optimized vs Unoptimized tools.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Component name inconsistent with displayed content

Low Severity

The component StarterToolInfo and file starter-tool-info.tsx now display content about "Unoptimized MCP Server" and "Unoptimized tools", creating a naming mismatch. This component is imported across 8+ pages in the codebase. Developers searching for "unoptimized" related code won't find this file. Consider renaming to UnoptimizedToolInfo or similar for consistency.

Fix in Cursor Fix in Web

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is acceptable for now. I didn't want to introduce a bigger diff, and we still refer to them in code as starter in some places as well. The "optimized" term is just a user-facing change.

@teallarson teallarson merged commit c84a3c7 into main Feb 5, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants